Importing InfoWorks CS/SD Network Data
InfoWorks CS/SD data can be imported from .cs2icm migration files exported from InfoWorks CS or InfoWorks SD.
To import a Catchment Group from IWCS/SD, right click on the Master Database icon or a Master Group in the InfoWorks ICM Explorer Window and select Import | Import model data from InfoWorks CS migration file... from the context menu, or click on a Model Group and select Import InfoWorks | Model group... | from InfoWorks CS migration file.
In IWCS/SD each type of database item, (e.g. Layer List, Rainfall Event etc.) is stored in a type group containing only that one type of data. Type groups will be imported into InfoWorks ICM as Model Groups.
The majority of data types are imported. The exceptions are:
- Graphs - the method by which graphs are displayed in InfoWorks ICM differs to that in IWCS/SD
- Graph Templates - the method by which graphs are displayed in InfoWorks ICM differs to that in IW CS/SD
- Workspaces - these can be recreated in InfoWorks ICM
Results and statistical reports are also not imported; however these can be regenerated by running the imported runs and recreating the reports from imported statistics templates.
Conversion Notes
The migration of supported IWCS/SD data items to InfoWorks ICM is straightforward for most data items. The conversion notes below include details of differences between IWCS/SD and InfoWorks ICM items.
In addition to database items, database data such as user permissions, user defined flags and user defined fields are also imported.
Networks
Due to version control and network object differences between IWCS/SD and InfoWorks ICM, some conversion is required when importing networks:
Child Networks
Networks that have been branched in IWCS/SD are imported as branched networks in InfoWorks ICM.
Child networks that are not branched in IWCS/SD are imported as successive commits in a single InfoWorks ICM network, named after the parent CS/SD network. The parent network and child networks can be opened via the commit history of the imported network.
Network Objects
IWCS/SD Flood Point and Flood Compartment objects are not imported as there is no equivalent to these objects in InfoWorks ICM.
IWCS/SD 2D Simulation Polygon boundaries and meshes are imported as InfoWorks ICM 2D Zones.
In IWCS/SD, the triangular elements of a 2D mesh are aggregated at run time and not at meshing time as in InfoWorks ICM. To view element aggregation in InfoWorks ICM it is necessary to re-mesh the 2D Zone after import.
For meshes imported from IWCS/SD that are not re-meshed in InfoWorks ICM:
- Aggregation of triangles will occur when running the simulation in InfoWorks ICM (as was the case in IWCS/SD)
- Results for the imported 2D zone will be displayed for each triangle instead of each aggregated mesh element
RTC Scenarios
IWCS/SD scenarios are imported into a network (containing no network objects) in an RTC model group. Each IWCS RTC will be imported as an InfoWorks ICM scenario associated with the network.
When importing an IWCS network, all runs using that network that also use an RTC scenario are found and used to create a list of RTC items. The network is imported with a scenario for each RTC item in the list named after the IWCS RTC item.
Layer Lists
MapObjects layer lists are converted to MapXtreme, or ArcGIS Engine/ ArcGIS Desktop layers lists. On import an Import Options dialog is displayed which allows the user to choose which of these formats to convert to.
Runs
Checked out networks are not exported by the IWCS exporter. If a run uses a checked out network, the run will be imported with missing networks.
Other referenced objects that have not been exported from IWCS will also be missing from the run when imported into InfoWorks ICM.
